Related
I cant run Gingerbread (GB) because many apps I use do not support such an old Android version.
So it must be between Ice Cream Sandwich (ICS), Jellybean (JB), and Kitkat (KK).
I've tried a few roms and cannot find the buglessness I seek:
[ROM] [4.1.2] [Mar 18 2013] Slim VJ Jelly Bean 4.1.2 - v1.0 for N1
VJ's previous non-slim JB rom
Evervolv's Kitkat
j00m's Kitkat
MIUI.us's unofficial JB port v2.12.28 (considerably worse than the official GB MIUI rom)
reider123's CM10 rom
tommypacker's pixeldroid AOKP kitkat
tommypacker's CM10.1.3 Android 4.2.2 v2.7
parkedraccoon's CM11
Evervolv ICS
All of them contain frustrating bugs. So the search continues to find the most workingest post-gingerbread rom.
Together, I'm sure we can find it! Who's got a lead?
And the winner is...
j00m's kitkat!
I'm using it on a 198/3/235 hboot (system is only 191mb)
one of the only roms besides official Evervolv that has trackball wake toggle (no more pocket wake-ups!)
on my recommendation, j00m replaced the /system/app/Torch.apk with one that stays on after screen turns off.
Tip: enable lock screen widgets in Security settings, and put the torch widget on the lock screen for quick access.
j00m fixed WiFi tethering (w/security set to None only)
i replaced the slow buggy stock kitkat browser with UCbrowser (it's even faster than dolphin)
i turned off the clunky window animations in Developer Options for a snappier experience
i installed the app Videocam Illusion to enable video recording
this is as bug free as it gets. Daily driver ready.
CM-11?
Sent from my Nexus One using xda app-developers app
Hmm, the only decent post-gingerbread ROM I found was Evervolv/J00m's KitKat. It works fine for me, but others haven't had such luck...Evervolv JellyBean (3.2.0 I believe?) was the best alternative, I can't remember what problem caused me to switch back to CM7. I think (if my memory serves me correctly) that one time it was the home button that wouldn't work, but the second time around it worked, I think it had something to do with running out of space, perhaps due to the GAPPS? Anyhow, you might give it a try and see if it works for you. Maybe try to flash the core GAPPS and get the play store to install your stuff instead of the full GAPPS which is way bigger.
I have the same problem with a 4.4 evevolv, the phone restarts constantly and gives me process.media was interrupted.
Leuviah said:
I have the same problem with a 4.4 evevolv, the phone restarts constantly and gives me process.media was interrupted.
Click to expand...
Click to collapse
Do a search, there's a fix for that.
Sent from my Nexus 7
BellaMay95 said:
Hmm, the only decent post-gingerbread ROM I found was Evervolv/J00m's KitKat. It works fine for me, but others haven't had such luck...Evervolv JellyBean (3.2.0 I believe?) was the best alternative, I can't remember what problem caused me to switch back to CM7. I think (if my memory serves me correctly) that one time it was the home button that wouldn't work, but the second time around it worked, I think it had something to do with running out of space, perhaps due to the GAPPS? Anyhow, you might give it a try and see if it works for you. Maybe try to flash the core GAPPS and get the play store to install your stuff instead of the full GAPPS which is way bigger.
Click to expand...
Click to collapse
Maybe I should give Kitkat another try... I remember having a delay to answer the phone on Kitkat... one time I kept waiting for the screen to turn on while it was ringing and ringing, and eventually i missed the call cuz there was no way to answer it.
Leuviah said:
I have the same problem with a 4.4 evevolv, the phone restarts constantly and gives me process.media was interrupted.
Click to expand...
Click to collapse
Actually, the solution isn't as easy to find as I remember. What worked for me was to clear data of media storage: Settings > Apps > All > Media Storage. Others have reported that they had to clear data of Contacts and Contacts Storage located in the same place.
Sent from my Nexus 5
PhilipTD said:
Actually, the solution isn't as easy to find as I remember. What worked for me was to clear data of media storage: Settings > Apps > All > Media Storage. Others have reported that they had to clear data of Contacts and Contacts Storage located in the same place.
Sent from my Nexus 5
Click to expand...
Click to collapse
I can not even get there, and it freezes before it restarts.
That recovery is to be used with black roses to install the 4.4?
Because the CM11 at the time of the flash failed?
Leuviah said:
I can not even get there, and it freezes before it restarts...
Click to expand...
Click to collapse
But you can reboot?
Are you on 4EXT recovery? Have you tried Evervolv KitKat 4.4.2?
Sent from my Nexus 5
PhilipTD said:
But you can reboot?
Are you on 4EXT recovery? Have you tried Evervolv KitKat 4.4.2?
Sent from my Nexus 5
Click to expand...
Click to collapse
You've tried the Evolv 4.4 kitkat, continually reboots and tells me that android.process.media was interrupted.
Now I installed the 11 cm, everything ok, except that the gapps did not install, and when I open mount2sd asks me to install a script, do the procedure but do not install and I get this error: Failed to reboot the device into recovery because the limitation of the rail toolbox
The 31-12-13 built is not useful at all. Its the worst. Try CM 11 an wait a few days for a update.
Nexus One using xda app
so the problem is the rom, gapps or are incompatible? if I wanted to put the Evolv, I have to change the hboot with blackrose? how do you?
Try evervolv ics rom. It is the least buggy and fastest rom there
Sent from my One S using xda app-developers app
cannondaleV2000 said:
Try evervolv ics rom. It is the least buggy and fastest rom there
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
This one?
Sent from my Nexus 5
How do I flash a hboot other than the stock black rose?
I lose my black roses?
There is no way to solve for the gapps?
cannondaleV2000 said:
Try evervolv ics rom. It is the least buggy and fastest rom there
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I'll give it a try.
@PhilipTD, yep, I think that's the one: [ROM] [DEV] [ICS 4.0.4] *7/1* Evervolv's Aosp TexasIce Cream Sandwich
hboot 220/10/206
I found a working download link to the final version of Evervolv's ICS rom (Evervolv-Perdo-2.2.0-Final-passion.zip): http://evervolv.codefi.re/builds/release/Perdo/
And its corresponding gapps: http://d-h.st/AxV
I tested Evervolv's ICS and immediately found 2 bugs that have been haunting me:
Cant play videos embedded in webpages.
Pressing the trackball to take a photo always requires 2 presses for the first photo.
So I gave the latest j00m's Kitkat another try, and while it's not bugless...
it seems to be the ONLY post-gingerbread rom that can play videos embedded in webpages.
Still has the camera-trackball bug. (is this bug present only in evervolv-based roms?)
Videocam illusion app works on EVERY rom for video recording.
Kitkat at least has the potential of fixing bugs as it is currently receiving very frequent updates.
So I think j00m's Kitkat is the way to go.
abemore said:
I tested Evervolv's ICS and immediately found 2 bugs that have been haunting me:
Cant play videos embedded in webpages.
Pressing the trackball to take a photo always requires 2 presses for the first photo.
So I gave the latest j00m's Kitkat another try, and while it's not bugless...
it seems to be the ONLY post-gingerbread rom that can play videos embedded in webpages.
Still has the camera-trackball bug. (is this bug present only in evervolv-based roms?)
Videocam illusion app works on EVERY rom for video recording.
Kitkat at least has the potential of fixing bugs as it is currently receiving very frequent updates.
So I think j00m's Kitkat is the way to go.
Click to expand...
Click to collapse
j00m's KitKat is really good. The only reason I switched to Evervolv's was because I wanted to try out ART on my device and that setting had been removed from the j00m's nightly...but ART doesn't work on my phone so they're both good for me. I might go back to j00m at some point since it is simpler to flash (don't need to flash GAPPS on top!) - plus it has a boot animation that has a clear start so I know whether my phone is in a bootloop or simply taking forever to load.
BellaMay95 said:
j00m's KitKat is really good. The only reason I switched to Evervolv's was because I wanted to try out ART on my device and that setting had been removed from the j00m's nightly...but ART doesn't work on my phone so they're both good for me. I might go back to j00m at some point since it is simpler to flash (don't need to flash GAPPS on top!) - plus it has a boot animation that has a clear start so I know whether my phone is in a bootloop or simply taking forever to load.
Click to expand...
Click to collapse
Additionally, j00m's rom is slimmed down to only 211MB system which means it should work perfectly on the ICS hboot - 220/10/206 saving lots of space!
The stock kitkat web browser is barely usable. Chrome browser is even worse. Thankfully, the Dolphin Browser works really well!
abemore said:
Additionally, j00m's rom is slimmed down to only 211MB system which means it should work perfectly on the ICS hboot - 220/10/206 saving lots of space!
The stock kitkat web browser is barely usable. Chrome browser is even worse. Thankfully, the Dolphin Browser works really well!
Click to expand...
Click to collapse
I've generally felt VJ's v6.0 4.2.2 was the slickest version of JB that I've used till date on my N1.
I've used PixelDroid, Carbon, PACMan, ParanoidAndoid and Evervolv. But while these ROMs are customizable and have different features, VJ's ROM had the perfect (imho) blend of CM and Vanilla Android which was right for me.
Video recording and Tethering won't work but the rest of the features are pretty cool. As far as KK ROMs are concerned, they are still not as smooth nor as stable as the JBs yet. I've only started playing around with @parkedraccoon's CM 11 and @texasice's 4.4. I expect better updates to follow.
SHORT VERSION: is there any stable rom for the i9305 that can also run banking apps that look at if your rooted? Or just a stable rom for i9305!? Or even a stock rom that has no bloat-ware (for i9305 of course and in uk)?
LONG:
So I started out a journey looking for a good stable rom and of course cyanogen caught my eye but I unfortunately swapped to a 4g service and swapped my phone right before embarking on this journey to a i9305 - crap!
I thought wow great 4g and 2gig ram it'll be perfect with cyanogen 11 so I waited and no M build for i9305 all year long argh! So I gave up and tried a nightly cyanogen 11 and it was buggy as hell. So gave up on that after a few weeks and trying different updates moved to carbon - again only nightly available even more bugs maybe I was just unlucky in timing but on to cyanogen 10.1 I was going backwards now not the most fun but it still has a few bugs but is way more stable and I loved the speed and camera was great but still it feels a bit old and I still prefer stock . So I am thinking now I either give up n get stock or go on to yet another one but im not confident now ...thanks!
i also like stock ROM...until now didn't found one which will have wi-fi working with stock kernel...so i will give it a try to rXTREME.JB.4.3-V5.1.1 with a custom kernel and see how it works...
spiderman07 said:
i also like stock ROM...until now didn't found one which will have wi-fi working with stock kernel...so i will give it a try to rXTREME.JB.4.3-V5.1.1 with a custom kernel and see how it works...
Click to expand...
Click to collapse
Hmm yes too many bugs in all the custom roms on this device wish I could try a cyanogen M build ...
if you want to install rXTREME you MUST make a full wipe....in instruction it says it is recommended....but in reality is a MUST...all kind of bugs...and freezes...just opened screen and tried to unlock it...light effect...instant freeze...had to reboot...
i also wanted a stable CM11....not with huge battery drain...and other force closes....
hi men ,
i used the slimKat rom on my gti9305 and it's the perfection for that
Try Pacman RC1 everything is working very very less Force closes though but I have flashed paranoid ROM gapps and Google play app is not connecting :/
Very less it works
Sent from my GT-I9305 using XDA Free mobile app
I flashed this recently. Its working PERFECT :good: :good:
(bloatware can be turned off)
performance improved, minimum ram usage, longer battery life (comparing to 4.3 stock rom)
NO PROBLEMS
[ 4.4.4] [ROM] [STOCK-Official] [I9305/I9305N]
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
I try ROMs and ROMs and ROMs and all are unusable, because the
phone freezes with nameless-5.1.1-20151107-p880-nightly or
reboots when starting apps with euphoria-os-1.1-p880-unofficial-20160208-user or
is extremely slow and is stottering with aosplp-20151122-p880
a..s.o
The apps which lead to a reboot with euphoria work fine with aosp and nameless. Euphoria is fast, faster than nameless, which would be fast enough for me. There are no problems which exist with every ROM.
Does anyone have a recommendation for a ROM for the P880 which works without big problems. At the moment I think about to go back to 4.4 and try beanstalk-4.4.4010-20140904-p880cm
Of course I would be happy to find a ROM with fixed stagefright-bugs, but it looks like to be impossible
lg-optimus said:
Of course I would be happy to find a ROM with fixed stagefright-bugs, but it looks like to be impossible
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/showpost.php?p=66049970&postcount=1195
This is the latest 5.1.1 ROM with security patch level at 2016-04-01. It has all known stagefright bugs fixed so far.
If you wish to report issues on the ROM I shared, then use the thread over there, not here.
MoltenMotherBoard is the last custom ROM that I miss to test. I'm going to try it in the next days.
According to my test, my answer to the thread question is: NO, there's no custom rom working fine for my daily use.
Actually fastest rom was liquid smooth 4.4.4. Our phone hardware outdated. Like the others said this phone is crap
I'm running Euphoria version 1.0-p880-20150130 (Android 5.0.2), it's the best Lollipop based custom ROM for our device in my opinion. Unlike AOSP it has more settings (& features), and it's more stable than later versions of Euphoria. If you want to stick to KitKat, check out the latest CM nightlies.
To be honest, after 2 years of testing custom ROM... today i finally found the best one to keep... STOCK!!!
I've re-discovered the pleasure of see who is calling me at once, not after 20 seconds. I can finally take photos, hear who is calling, open apps without having to wait like 20-30 seconds.
I appreciate the effort of every developer... but at the end, the result is that out of 20-30 custom ROMs for our phone... no one can be used for daily use and being happy with it
bs360 said:
To be honest, after 2 years of testing custom ROM... today i finally found the best one to keep... STOCK!!!
I've re-discovered the pleasure of see who is calling me at once, not after 20 seconds. I can finally take photos, hear who is calling, open apps without having to wait like 20-30 seconds.
I appreciate the effort of every developer... but at the end, the result is that out of 20-30 custom ROMs for our phone... no one can be used for daily use and being happy with it
Click to expand...
Click to collapse
having JellyBean running on your device in 2016 is a very very very bad idea.
Here's the issues I found with LG stock JB-4.1.2 ROM v20 euro-open. If you can live with them, then good for you.
- Bluetooth button action broken. Cannot invoke Google Search or Voice Dialer from bluetooth headsets. Fixed in custom ROM such as CM/AOSP KK and LP.
- No update for Google Maps. Version 7 is the final version for v20c. Fixed in CM/AOSP KK/LP.
- No notification from Lock Screen. Fixed in CM/AOSP LP.
- No smart lock to avoid the hassle of entering PINs for known location and known BT device. Fixed in CM/AOSP LP.
- No screen cast. Fixed in AOSP LP.
- No bluetooth tethering. Fixed in AOSP LP.
Actually I'm on stock now (euro 20c), and my version of Maps is 9.25.1.
But yes, you're right...I'm ok because for instance I don't use bluetooth at all.
I still miss to test "AOSP Lollipop 5.1.1 | MoltenMotherBoard"...but my question is: is smooth as the stock? Are these working ? camera, flash, barcode, dialer reader, calls in general..
thanks in advance
bs360 said:
Actually I'm on stock now (euro 20c), and my version of Maps is 9.25.1.
"AOSP Lollipop 5.1.1 | MoltenMotherBoard"...but my question is: is smooth as the stock?
Click to expand...
Click to collapse
When I was still on LG stock JB, Maps somehow got updated. But then the device slowed to crawl and I factory reset it and I didn't get Google Play store to update it again. Glad you have it and it works for you.
Barcode and FM radio are not working. If these 2 are important to you, then you should stick with LG stock.
For UI smoothness, I think Lollipop itself has made tons of improvement that it is at least the same or better than JB. Don't take my words for it, you should try it out yourself and pass on the judgement.
I reinstall again LS KK 4.4.4 and updated to latest Mourta's kernel from modaco forum. Phone back to alive.
asgz said:
I reinstall again LS KK 4.4.4 and updated to latest Mourta's kernel from modaco forum. Phone back to alive.
Click to expand...
Click to collapse
please link?
LS 3,2 4.4.4 and mourta's kernel inside of the file. I installed rom and open gapps after a few days wiped cache and updated kernel.
here is the link : http://s4.dosya.tc/server/uqoebl/LS_KK_4.4.4.rar.html
asgz said:
LS 3,2 4.4.4 and mourta's kernel inside of the file. I installed rom and open gapps after a few days wiped cache and updated kernel.
here is the link : http://s4.dosya.tc/server/uqoebl/LS_KK_4.4.4.rar.html
Click to expand...
Click to collapse
i just get an loop bot, i can't install a kernel..
Does anyone know how to fix the Ok Google voice function in android 7? It only works in the Google app and not everywhere.
tApPeD fROM mY nExUs 6
This works, if not try to do it with an older version of google app, and then update to latest beta
http://forum.xda-developers.com/showpost.php?p=69190540&postcount=82
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Strephon Alkhalikoi said:
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Click to expand...
Click to collapse
Just installed cyanide and it works very well
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Strephon Alkhalikoi said:
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Click to expand...
Click to collapse
No, i don't think so, it runs on aosp too, nitrogen
for example
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Strephon Alkhalikoi said:
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Click to expand...
Click to collapse
i actually think its a google now issue. both my lg k7 and lg blahblahblah both had it working on any screen, then it stopped working, and options disappeared. a few days later, the options reappeared, i enabled them, and now works again on any screen.
I guess I didn't word things quite right, as I meant to say the interaction between the Google app and ROM was causing the issue. Hopefully you're right about it being app related so I can move back to Pure Nexus.
I'll give it a shot... I'm running Chroma MM and it works but not in Nitrogen OS. I think it was working on the sky dragon ROM but I was having corruption issues on boot with it while using multirom.
tApPeD fROM mY nExUs 6
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Strephon Alkhalikoi said:
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Click to expand...
Click to collapse
Sorry to rehash this but it's a bit of a bump. It's actually not Google's fault. OoenGapps made a change back in September, changing HotwordEnrollment.apk. okGoogle anywhere has been broken ever since. It's only happening to AOSP Roms like the person above stated. The maintainers of CM for the 6P are trying to get to the bottom of it to see if they can do anything to fix the issue.
MrBrady said:
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Click to expand...
Click to collapse
Try to freeze the hotword enrollment apk.....I use ROM Toolbox Pro for this. It is a system app.....froze it and then followed the directions around the forums and google assistant worked for me on nitrogen on screen off, it seemed to me to be a little more "finicky" at starting from screen off then on stock, but that could just be me and how my voice training was saved or whatever....good luck
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
You can't use an M kernel on N or vice versa. Won't work.
joseph230 said:
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
Click to expand...
Click to collapse
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
I flashed radio of 7.1.1 over 6.0.1 and it did not cause any issues. This is a proof to what you just said. Kernel is full of bugs and that is hard to fix
Sticking with 6.0.1 for now! Maybe I should get back into using custom roms again!
Thanks.
joseph230 said:
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
Click to expand...
Click to collapse
Heck 98, XP and 7 were the only good ones. Dont even get me started on 10. I had to go back and revert over 300 PC to windows 7 when the 10 upgrade happed. That was just a nightmare.
What sort of issues are you talking about? Besides the speakerphone echo.
zelendel said:
Your issue is 7.1.1. Android N is full of issues...
Click to expand...
Click to collapse
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Lawstorant said:
What sort of issues are you talking about? Besides the speakerphone echo.
Click to expand...
Click to collapse
Wifi and Radio connection drops all the time. Many people seem to experience it!
NLBeev said:
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Click to expand...
Click to collapse
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
joseph230 said:
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
Click to expand...
Click to collapse
It seems to me that Google changed policy.
Till now the changes made the N6 great again.
No encryption, dark interface when possible.
Aquamail is better than Gmail, Signal is better than G-messenger. Nova launcher is better than G-now launcher.
I replace/disable G-apps and G-services when possible.
No Google Assistant, no Fit, no Pay, no Game, no Hangouts, no Wearable, no G-drive, no G-now.
Runs smoothly, no issues. Excellent battery life. Good to have XDA.