Well I got permission from zarboz to use this kernel, but having problems with WiFi. Tried with sun_dream sense 5. Tried wiping cache and factory reset still same problem going to try on stock. Well tried on medusa Rom same problem. Must be in kernel. Any help would be appreciated and welcomed.
https://www.dropbox.com/s/rzsbypd1ft758ir/Myst_4.2.zip?dl=0
Sent from my HTC first using XDA Free mobile app
The more info we can gather the easier it will be to find a fix for this. So if someone can test this out and give us some feedback, thank you very much .
Is there any other kernel for this phone that has WiFi working? Maybe I could try to get the WiFi piece from the good one and put it into this one.
The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app
blafree64 said:
The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
after flashing this kernel, could you do this for me:
1. Flash UKM http://forum.xda-developers.com/android/software/zip-synapse-script-universal-kernel-t2736986
2. Install "synapse" (its an app), reboot
3. Go into synapse, you should now be able to configure the kernel (if you still cant, refer to the link above).
4. Post screenshots of EVERYTHING
5. Upload your build.prop (/system/)
i wish i had a first i could go through the file system myself.
Edit:
Hopefully stock android filesystems stay the same from version to version. im on 5.0 at the moment on my nexus but try some of these things too:
1: delete this folder /data/misc/wifi/ And /data/misc/dhcp and system/etc/wifi reboot. (try deleting 1, then reboot, then if it doesnt work, delete the first 2 folders, reboot, if that doesnt work, delete all 3. try different combos).
(and/or)
2: force stop Bluetooth Share (i think you can go to apps>all> and find it there. reboot
3: drain the battery to 0. like make sure the thing is DEAD and wont boot even into recovery. let it sit for some time. plug in your charger and turn it on at the same time.
here is some additional info. if you want to try this. go right a head!
jpsflores said:
Hello all!
I registered here so that i could share a possible solution to the stuck wifi problem. On my nexus the BT was also stuck most of the time.
Been having the problem for about two weeks and was about to do a clean install and, if the problem persisted, call Google support. Thing is, I had the feelling it was software related and that the hardware was ok.
I´m not sure if BT, Wifi and NFC use the same hardware but the fact was that wifi worked for a few days, BT for a few more and NFC was always functional.
I did some extensive research thru the web and it seemed that this problem was not nexus unique and seemed to be related with wpa_supplicant.conf or wpa_supplicant in the bin file.
On this page, mind you the text is pretty old and not entirely android related:
http:_//_blog.linuxconsulting.ro_/2010/04/porting-wifi-drivers-to-android._html (I can't post links yet so just copy past and remove spacing)
I found this little snippet that caught my attention:
Seems that you can add ap_scan=1 to your wpa_supplicant.conf depending on the drivers you have.
After some more research on the subject of ap_scan i found that:
It seems that addind ap_scan=1 imposes that wpa_supplicant.conf handles the scanning and AP selection. IF there's something wrong with the driver, and not with wpa_supplicant as i originaly thought, this could bypass the problem.
So I added ap_scan=1 just before the device identification lines in wpa_supplicant.conf, reeboted, and now the wifi and bluetooth toggle normaly. I've tried ap_scan=0 (the driver handles the scanning) and the problem returns, so ap_scan=1 does allow you to toggle the wifi and BT on.
I can't yet verify that the phone actually connects to a wireless network and has the same stability and range as before as I'm at work and there's no wireless here.
Therefore I ask for your help to verify this "fix" and thoughts on this.
Sorry if the post is a mess. Both english and programming aren´t my native languages...
My device is a Nexus 5 with stock 4.4.4 KitKat and root.
Greets.
---------- Post added at 10:29 AM ---------- Previous post was at 09:46 AM ----------
So, quick update:
Managed to find an wireless network around and connected to it. Some time later, no sure how much, the phone rebooted.
Some time after that the wifi and Bt were stuck again. Accessed wpa_supplicant.conf and deleted the new wireless network information. Rebooted and all was functional again.
Seems the fix is incomplete as any rewrite of the wpa_supplicant.conf reinduces the initial problematic behaviour...
____________________ Extra Update_______________________
Ok, so it seems that the wpa_supplicant.conf is suposed to have ap_scan=1 by default.
After boot and when I connect to a wifi network my file resets and shows without ap_scan=1 and instead of:
ctrl_interface=wlan0
its
ctrl_interface=data/misc/wifi/sockets
Wifi with a conf. like this never works. If I manualy "correct" the file and reboot, the wifi toogles on, but after a wifi connect gets busted up again.
by now I've done:
- copy wpa_supplicant (the bin file) from a stock 4.4.4
- Check file permissions for all wpa_supplicant files
- dirty flash the stock build (it's my original build so less harm done i guess)
- 2 Clean installs
- 6 factory resets
And the problem persists.
I've called google support and they are sending a new phone as we speak. Now I'm not sure if it's a software or hardware problem (maybe a combination of the two?) but I figured it would be better to reroll a device instead of trying to fix this one as this problem is cleary out of my league.
Thank you all!
Click to expand...
Click to collapse
Cannot download synapse playstore is incompatible ugh..
Sent from my HTC first using XDA Free mobile app
This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app
blafree64 said:
This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Yeah all end correct. Try the steps I posted to fixing Wi-Fi hopefully it will work
BTW. Are you running android 4.4? I thought HTC first is only 4.1
I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app
blafree64 said:
I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Is everything working?
All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app
blafree64 said:
All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Alright.
If you need any more help let me know
I'll do my best
Related
This rom is based from zukriaksah's miui 1.12.16. His had a good foundation just some issue. I have made some changes to it and so far things are working (keep in mind that this has not been tested for a little more than 2 days).
Link https://docs.google.com/open?id=0B6a1DYyFKfu1YjI4MDg0YTEtZGExOC00ZGZkLTg4MGEtMmM0Y2ZjYTQwYzlh
(sorry file are on work pc and this is the only way that I can get them up...so if some one can move to a better site for downloading...pls feel free to do so)
you will have issues with wifi on this rom - the work around that I used it to load cacingkalung's modded version of the sd kernel...get it here http://forum.xda-developers.com/showpost.php?p=20326475&postcount=240
had to change the build.prop this phone keep rebooting with some of the files that I had to switch out. I used files from tj and issac.
usb and headphone issues are gone (so far)
added the miui 4-way reboot (hold power button for options)
the fm radio that is in the rom fc's (wish someone can fix this..I am at a loss, I know that it has to be a driver issue but I have no clue which one have been searching for weeks it seems to correct this...I really miss the radio)
added some init.d tweaks...these are found in the various forums here on xda
you might have to load script manager to get them to work (I load this anyways so I dont know if it is needed)
what I added to the init.d:
10cpu - sets the cpu values and govenor
11 iosched - set i/o scheduler
both of these you do not need if you use setcpu or other program like it...I just dont like to have these loaded they take up space and memory.
80netspeed - internet speed hack (helped on mine)
97ks - some kernel mods - helps rom run smoother in my opinion
98kt - internal task killer values
you dont need these you can remove them...play around with the settings you might be able to tweak the rom more to you liking...these are the values that worked best for me
I dont have much of a clue on the battery life yet...have had phone up and down so much that I have not let it go threw my daily pace
So far things seem stable...still no HDMI, dont know if we will ever have this...I am not that good with dev have look at other roms but if the drivers aint right it wont work
I also use force2sd to move the programs to the sdcard to free up the internal memory...everytime that I have tried to include apps2sd thing go wrong..this way works for me so I am not going to worry about it
you will probably get unknown for the carrier...if you know your spn values you can edit it and the name will show up...there are progams in the market that will fix it...other have had luck with out needing a program...In the miui forums they have miui extra setting and they say that you can use it to change the carrier name (never tried)
make sure that you do a system wipe before installing....I dont know what issue you will get if you dont
**latest update**
http://forum.xda-developers.com/showpost.php?p=20803286&postcount=35
Thanks for helping me
Sent from my CSL-MI410 using xda premium
zukriaksah said:
Thanks for helping me
Sent from my CSL-MI410 using xda premium
Click to expand...
Click to collapse
zukriaksah, not a problem, hopefully we can get hdmi and fm working
can someone post the austrie kernel in a seprate thread so everyone can see it with wifi module of course
cowsgo said:
zukriaksah, not a problem, hopefully we can get hdmi and fm working
Click to expand...
Click to collapse
FM Radio Not Work Open FC
preyesh1 said:
can someone post the austrie kernel in a seprate thread so everyone can see it with wifi module of course
Click to expand...
Click to collapse
preyesh,
Here you go:
http://forum.xda-developers.com/showthread.php?t=1407689
mibsut said:
FM Radio Not Work Open FC
Click to expand...
Click to collapse
Please read carefully... As they say, they are trying their best to make the hdmi and fm working... please be patient and hope they can overcome the problem. And to be honest, its not an easy task... So, just wait and give the developers some time to fix it.
preyesh1 said:
can someone post the austrie kernel in a seprate thread so everyone can see it with wifi module of course
Click to expand...
Click to collapse
what is that kernel? for miui? if yes for which version?
---------- Post added at 10:48 PM ---------- Previous post was at 10:42 PM ----------
ohh got it ... the SD kernel
anyone who tries the kernel please update on battery backup
cowsgo said:
This rom is based from zukriaksah's miui 1.12.16. His had a good foundation just some issue. I have made some changes to it and so far things are working (keep in mind that this has not been tested for a little more than 2 days).
Link https://docs.google.com/open?id=0B6a1DYyFKfu1YjI4MDg0YTEtZGExOC00ZGZkLTg4MGEtMmM0Y2ZjYTQwYzlh
(sorry file are on work pc and this is the only way that I can get them up...so if some one can move to a better site for downloading...pls feel free to do so)
you will have issues with wifi on this rom - the work around that I used it to load cacingkalung's modded version of the sd kernel...get it here http://forum.xda-developers.com/showpost.php?p=20326475&postcount=240
had to change the build.prop this phone keep rebooting with some of the files that I had to switch out. I used files from tj and issac.
usb and headphone issues are gone (so far)
added the miui 4-way reboot (hold power button for options)
the fm radio that is in the rom fc's (wish someone can fix this..I am at a loss, I know that it has to be a driver issue but I have no clue which one have been searching for weeks it seems to correct this...I really miss the radio)
added some init.d tweaks...these are found in the various forums here on xda
you might have to load script manager to get them to work (I load this anyways so I dont know if it is needed)
what I added to the init.d:
10cpu - sets the cpu values and govenor
11 iosched - set i/o scheduler
both of these you do not need if you use setcpu or other program like it...I just dont like to have these loaded they take up space and memory.
80netspeed - internet speed hack (helped on mine)
97ks - some kernel mods - helps rom run smoother in my opinion
98kt - internal task killer values
you dont need these you can remove them...play around with the settings you might be able to tweak the rom more to you liking...these are the values that worked best for me
I dont have much of a clue on the battery life yet...have had phone up and down so much that I have not let it go threw my daily pace
So far things seem stable...still no HDMI, dont know if we will ever have this...I am not that good with dev have look at other roms but if the drivers aint right it wont work
I also use force2sd to move the programs to the sdcard to free up the internal memory...everytime that I have tried to include apps2sd thing go wrong..this way works for me so I am not going to worry about it
you will probably get unknown for the carrier...if you know your spn values you can edit it and the name will show up...there are progams in the market that will fix it...other have had luck with out needing a program...In the miui forums they have miui extra setting and they say that you can use it to change the carrier name (never tried)
make sure that you do a system wipe before installing....I dont know what issue you will get if you dont
Click to expand...
Click to collapse
thats great.......
but I am not able to download.............. can some one who already downloaded can upload on other site as this download link is not working with me ...
guys, can you make softkey vibrate?
thanx for the build cowsgo!
does the front camera flip-up? last time i used ur build the front camera is working fine, but after flashing cacingkalung's SDKernel it flipped up
hey COWSGO thanks for this.... can you please resolve the headphone and wifi issues for 1.12.2 build.... I really liked that 1.12.2
Perhaps this is the last version we stay on gingerbread. Keep on and go stable.
Sent from my CSL-MI410 using XDA App
To easily download frm google docs, 1st dont use stock browser, use 3rd party, eg. Opera mini, 2nd change yr google docs view to desktop mode
Sent from my CSL-MI410 using xda premium
anyone having problems with bluetooth? i cannot seem to activate it.
mi410 said:
hey COWSGO thanks for this.... can you please resolve the headphone and wifi issues for 1.12.2 build.... I really liked that 1.12.2
Click to expand...
Click to collapse
mi410, I will look at this after the holliday
emt said:
anyone having problems with bluetooth? i cannot seem to activate it.
Click to expand...
Click to collapse
emt,
I will look at the files and see what I missed for the bluetooth. Sorry I dont use it so I didnt test it.
hey COWSGO..... really thanks for the this beautiful ROM.
quite smooth ...... experience .....
really happy with the ROM.
next time when you update the ROM with Bluetooth wish following update also ....
1. Camera if possible (Front)
2. Time should be at center of status bar like what you did with 1.12.2
3. FM if you able to repair ....
enjoy your holidays .....
Dont know if anybody has gps issues or proximity issues....I did....this is what I did to solve this
use root explorer goto system\lib\hw and rename two files to .old
the files are gps.fb0.so and sensors.fb0.so
then goto settings click programs and goto call settings and turn off enforce proximity (what ever the option is under use proximity sensor
reboot....after I did this the sensor works with incoming and outgoing calls and the gps locks in under 30 seconds. used gps status from the market to confirm...dont for get the you might have to edit the gps.conf file in system\etc (I think)...if you didnt edit this file after you loaded the rom then it will be set for north-america.
dont know why this worked....has to be a issue in the files...when I get more time I am going to decompile them to see what is different
[UPDATE]2012-08-06 This is not the only way of getting Dongle's working on Android, If widgets are your thing and you doing feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android.
[UPDATE]2012-08-06 The source to libhuaweigeneric-ril ( github ) has been updated to include fixes made by omegaRed7 - This massively improves the fault tolerance upon RIL Startup, Tests were carried out on the E173s-1 but it should be beneficial to all modems ( I hope ).
[UPDATE]2012-07-28 As the Rom Version is quite old and it doesn't really require it's own rom I've extracted the files required to implement this functionality - Download Here, The Archive contains a README file with installation instructions
IMPORTANT - pppd permission need changing to 6755 also change to ownership to the root account ( Thanks to __DS__ ). you can do this through adb or terminal emulator
Code:
adb shell chown 0:0 /system/bin/pppd
adb shell chmod 6755 /system/bin/pppd
for this to function
[UPDATE]2012-06-25 Added Forked libhuaweigeneric-ril to Github Repo this includes all the changes I've made - Check This Post For Details
[UPDATE]2012-06-23 Added Github Repo - Check This Post For Details
[UPDATE]2012-06-16 THE DOWNLOAD LINK HAS BEEN UPDATED AS THE FILES IN /etc/system/usb_modeswitch WHERE NAMED INCORRECTLY[/UPDATE]
Hi Folks - This post is going to change fairly often, there is still more info to add, I just got bored with typing for now
The Sales Pitch
This rom aims to provides the same "hands free" approach offered by the Archos 3G Key and extends this functionality to Huawei Branded USB Modems.
Introduction
Here is a custom rom I've currently been hacking away at, if feels like I've had it under wraps for months.
That being the case. I'd like to thking on to enable Huawei USB Modems - This is still a WORK IN PROGRESS but It feels like i've been keeping it under wraps for months, So it's time to throw it out there for further testing. So Dongles at the Ready! It could get a little hacky
WARNING
The Full Size USB Slot has been known to fail from moderate use. As such I would recommend using an USB extensions cable for connecting devices.
VERY IMPORTANT NOTES - PLEASE READ
1. This is definitely not an every day use rom on any other device this woud have been deployed as a recovery flashable update. The reasoning behind the rom deployment is it's only one file to copy and youi're ready to go. It is also a tedious task to manually go through (especially on the 100th time
2. Please don't ask a me if a certain device will work or not. It is not helpful on a number of levels,
a) I simply don't know - I don't own the model in question. Further more you can figure it out yourself.
b) The Chances are that you could probably find out the answer without leaving the comfort of xda - The libhuaweigeneric-ril has been passed around xda like a <Insert Well Used Analogy Here> so a quick search of xda may turn up something useful to reassure you.
c) In reality though we are not going to know if your dongle is working until you "Try It Yourself".
3. if you find your device doesn't work then you need to gather all the relevant information to help get a feel of what's going on; See Below
SUPPORTED DEVICES
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
IMPORTANT NOTES - WHAT YOU NEED TO KNOW
In a perfect world you can download/flash the attached update file. Reload your SDE, Plug a USB 3G Dongle and have It connect and go about you day .
This is the ultimate goal and currently what happens on my own device
TROUBLESHOOTING
There's about a 25% based on my current test this won't happen. There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprops
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
Please have a glance over it before posting as It may contain information that you would not want others to see!
ROM DETAILS
Android Version: 4.0.3
Archos Version: SDE 4.06
Removed : Nothing
ADDITIONS
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
DOWNLOAD
3G Modem Redist Pack - For use with newer roms
Hotfile - archos.ext4.update.
INSTALL
Unpack zip and copy unpacked update file to the device
Code:
adb push archos.ext4.update /mnt/storage
restart device in sde mode
script should update automatically
KNOWN ISSUES
"3G Stick Connected" Icon remains in notification list after device disconnection.
pppd needs to be executed with elevated privileges.
pppd is not exiting correctly on some occasions and cause reconnection issues when using multiple sticks.
Thanks go to surdu_petru for the base sde, derAtem for his original work on the libhuaweigeneric-ril.so and pretty much every developer who has worked on these dongles with android, I think I've read every thread on XDA regarding this subject
Hi!
Thanks trevd!
I do not have this USB modem ....but you did a good job for those who have this modem ! Good luck...
i have a Huawei E160E
It is possible to add this modle on your rom ?
---------- Post added at 06:46 PM ---------- Previous post was at 06:23 PM ----------
For the buzz in FRANCE (and in the World :-= )
http://www.jbmm.fr/?p=28280
cajl said:
i have a Huawei E160E
It is possible to add this modle on your rom ?
Click to expand...
Click to collapse
Is this a new model ( released this year )? It may already be in there, The easiest thing to do is plug it in.
If you install this app you can find out what the product_id is and then we can find out for sure.
Thanks
no released in 2009
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 12d1
Vendor Name: Huawei Technologies Co., Ltd.
Product ID: 03eb
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Rackham666 said:
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Click to expand...
Click to collapse
Hi Rackham666
I'd refer back to my first post, I've tried to make it a little more clear what this "rom" exactly is, more a testing ground, my apologises if that wasn't very clear at first glance, So to switch this query right back at you.
After installing my rom, I'd like to know if your Huawei K3565 is supported?.
For my usn dongle , is it ok for you ?
Okay.
I'll try your additions manually when [email protected] V3 will be released by Petru.
Get The Code
Hi Folks.
I've started a github repo if anyone wants to hack on this stuff.... It only contains the code for the hotplug service at the moment but I will obviously add more when I get chance and apply all the proper GPL licenses to it.
A personal word of note : C is not my first language by any stretch ( although it is fast becoming the case ) so If It causes any memory leaks or starts nuclear war I can't be held responsible, however if there is any noob coding errors in there then I'm ready to learn off those more knowledgeable than I. I have a feeling we have some hardcore developers lurking in Archos Development community
Equally If anyone has any fixes drop me a pm and I'll sort commit access on the repo or post them right here in the thread,
The code can be found here https://github.com/trevd
Hi Folks, Me Again!
Just to let you guys know I've added a forked libhuaweigeneric-ril to my github ( https://github.com/trevd )
It includes the changes I made to enable it to work the Archos.
You'll want to clone the ics branch if you want to compile yourself.
cajl said:
For my usn dongle , is it ok for you ?
Click to expand...
Click to collapse
???
I'm not sure I understand what you mean.... can you explain a little more
Thanks
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
Hi Alahkel
You're not bothering me .... DO I really sound/come across as that grumpy/angry in my first post.... sometimes I get cranky when I don't get enough sleep.... too much time looking at code.... :laugh:
Thanks for having a go, Are you using the official SDE? and have you got a working SDE Rom already installed?
For now I would forget about the rom image and bear with me, I'm working on an installer APK which will probably better help with testing, I'll also put the manual installation method up for those who want to get dirty with adb.
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
trevd said:
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
Click to expand...
Click to collapse
Hi, thx for answering. Well of course I turn on the 3g key in settings for big-size usb and my huawei 3gkey is on indeed (led on key) but the tab doesn't recognize that o.o I'm on tim (italy ) Thank you
Sent from my ARCHOS 101G9 using xda premium
Hi trevd,
i'm guessing this won't work on CM9 by JackpotClavin, or would it? If yes, would i install it the same way as described?
Thanks in advance!
Edit: Sorry i'm obviously still running in 1st gear in the morning... There's no 3G support in the CM9 port so there's no way this would just "work"...
Edit2: And confirmation that i need more coffee: Saw your post in CM9 thread about the successful connection with Archos' 3G stick and a Huawei 3G stick, but only through the browser... Any progress on fixing things so the ppp connection is fully usable by other apps & services?
Hi, trevd!
how to launch the modem on a firmware 4.0.7?
I copy these files from your firmware
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
Click to expand...
Click to collapse
I change the init.rc file for init.dongle.rc start
but the Huawei E1550 modem doesn't work
what it is necessary to change still?
Thanks!
=========================
sorry, everything earned, it was necessary to update a modem firmware
Hi deman05
You were nearly there, init.dongle.rc is imported on the very first line of init.rc so you need both files.
You shouldn't have to do anything with the modem firmware as usb_modeswitch will handle turning the modem.
The files required are.
init.rc
init.dongle.rc
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
/system/bin/hotplugd
Also you need the full contents of the following directories
/system/etc/usb_modeswitch
/system/etc/ppp
/system/etc/chatscripts
I've attached the latest versions to this post (hopefully I've not missed anything), you will need to change the permissions on /system/bin/pppd.
chmod 6755 pppd
[EDIT] I did miss something, please see the first post for the correct download link.
The new version also handles a cold boot ( modem plugged in on startup ) scenario.
If you are still having issues please refer to the troubleshooting section in my original post
Thanks
Any conversation having to do android 4.2.2 goes here. If the ROM you want to talk about has a thread. Then go there!
Here is my PAC rom. can someone please test this? Just flash it like any other 4.2.2 rom. wipe then flash rom and then GAPPS. Please tell me if it boots and if you have time could you obtain a logcat?
http://d-h.st/9jb
Mobile Data seems on my version seems to be connected, but instead of toggling Mobile Data on and off the H just keeps appearing and disappearing.. But it says AT&T in the notification drawer. I will flash your version and try it out once its done downloading.
---------- Post added at 03:12 PM ---------- Previous post was at 02:17 PM ----------
camo_flage said:
Here is my PAC rom. can someone please test this? Just flash it like any other 4.2.2 rom. wipe then flash rom and then GAPPS. Please tell me if it boots and if you have time could you obtain a logcat?
http://d-h.st/9jb
Click to expand...
Click to collapse
First try, stuck on bootscreen.. flashed rom, gapps then 6/30 kernel, will try reflashing with just rom and gapps initially.
Whats the easiest way to get a logcat? I'm still not too sure how to make those of use but I know they are handy
---------- Post added at 03:43 PM ---------- Previous post was at 03:12 PM ----------
Second try, sticks at bootscreen for +10min still. Flashed rom then gapps.
Here is my version that boots, mobile data doesnt work but I can send and recieve texts, and WiFi works... Also no storage.
http://d-h.st/qYQ
Flash ROM zip then gapps, booted within a few minutes for me.
calikevin said:
Mobile Data seems on my version seems to be connected, but instead of toggling Mobile Data on and off the H just keeps appearing and disappearing.. But it says AT&T in the notification drawer. I will flash your version and try it out once its done downloading.
---------- Post added at 03:12 PM ---------- Previous post was at 02:17 PM ----------
First try, stuck on bootscreen.. flashed rom, gapps then 6/30 kernel, will try reflashing with just rom and gapps initially.
Whats the easiest way to get a logcat? I'm still not too sure how to make those of use but I know they are handy
---------- Post added at 03:43 PM ---------- Previous post was at 03:12 PM ----------
Second try, sticks at bootscreen for +10min still. Flashed rom then gapps.
Here is my version that boots, mobile data doesnt work but I can send and recieve texts, and WiFi works... Also no storage.
http://d-h.st/qYQ
Flash ROM zip then gapps, booted within a few minutes for me.
Click to expand...
Click to collapse
Damn must have did something wrong
---------- Post added at 08:17 PM ---------- Previous post was at 08:04 PM ----------
camo_flage said:
Damn must have did something wrong
Click to expand...
Click to collapse
Well I think you should contact albinoman to help sort out the issues...for now I will try to build AOKP because you seem to have PAC covered
Also I am going to switch devices to the amaze for the port because the Vivid and the Amaze are 99% the same internally. Unfortunately, the Amaze does not have a PAC rom . Dang I wish homeslice would come back to the Vivid and help us out with this.
Log cat...
Connect to PC
Make sure adb works...
Type adb logcat
Orrr
Type adb logcat > yourfilename
Sent from my Vivid 4G using Tapatalk 4 Beta
Calikevin I think you have to start building from source now if you want to fix the issues in PAC
Sent from my Vivid 4G using xda premium
I have built CM10 itself from source, but I have no idea how to go about combining source from the port I want into the CM source, that's still a little advanced for me but I will try and figure it out nonetheless
Sent from my Vivid 4G using Tapatalk 4 Beta
Yea that's what I was worried about too.
Sent from my Vivid 4G using xda premium
I am currently syncing the SlimBean repo right now to get started on combining the source but if anyone has any useful links or advice I would greatly appreciate the input
You guys taking requests?
I'd love to see Vanilla Rootbox...
Sent from my Vivid 4G using Tapatalk 4 Beta
rignfool said:
You guys taking requests?
I'd love to see Vanilla Rootbox...
Sent from my Vivid 4G using Tapatalk 4 Beta
Click to expand...
Click to collapse
I don't see why not, I've got a few ideas of my own already, I'm this close to having BAKED holiday built, then I would like to see about Illusion.. I did see Vanilla Rootbox too, I'll check it out.
I'm happy that the Vivid development is still alive. Installed the rom, and its running smoothly. Rogers variant.
arzzzae said:
I'm happy that the Vivid development is still alive. Installed the rom, and its running smoothly. Rogers variant.
Click to expand...
Click to collapse
Check the link in my sig for the most updated Slim release
calikevin said:
Check the link in my sig for the most updated Slim release
Click to expand...
Click to collapse
Will do! Anyways, how do I decrease the overall font size for 4.2.2? It seems missing from the settings.
Edit: Seems like the whole "display" under the settings is missing.
Edit #2: Nevermind, I'm stupid. Found it.
Yea, still working in figuring out the Display force close, it would seem that an entire chunk of android 4.2.2 is missing from the ROM, probably has to do with the vivid.. 4.2.2 has Daydream, and its there in this ROM too but you usually need to go to Display settings to see the options and ours isn't there, but I was able to access the Daydream settings by going through the DashClock settings. Very odd, hopefully sultan or albinoman have some ideas about that
Sent from my SlimBean Vivid 4G using Tapatalk 4 Beta
android1234567 said:
You can delete the useless device trees by modifying the default.xml file (platform manifest) located in .repo/manifests
Click to expand...
Click to collapse
After adding an htc holiday device folder to the .git folder and trying to run git commit -a I keep running into this same error, any idea?
Code:
fatal: 'git status --porcelain' failed in submodule device/htc/holiday
calikevin said:
After adding an htc holiday device folder to the .git folder and trying to run git commit -a I keep running into this same error, any idea?
Code:
fatal: 'git status --porcelain' failed in submodule device/htc/holiday
Click to expand...
Click to collapse
Don't mess with the .git folders. The only file you have to modify to alter the entire source is .repo/manifests/default.xml
You can add and remove device trees by modifying that file, and you can change where existing device trees are fetched from (i.e. you can make an existing device tree be fetched from a different GitHub account instead).
android1234567 said:
Don't mess with the .git folders. The only file you have to modify to alter the entire source is .repo/manifests/default.xml
You can add and remove device trees by modifying that file, and you can change where existing device trees are fetched from (i.e. you can make an existing device tree be fetched from a different GitHub account instead).
Click to expand...
Click to collapse
Thank you!
So for instance.. this is in the default xml for Baked-
Code:
<remote name="baked"
fetch="git://github.com/TeamBAKED/" />
If I change that address to my github address, I will be able to repo sync and git commit from my own repo, and be able to upload the device trees you were trying to take a look at?
And it's safe to take out every one of these except holiday since that's all I'm building for?
Code:
<project path="device/htc/m7ul" name="device_htc_m7ul" remote="baked" revision="jb-4.2" />
My wife has and A&T HTC Vivid phone. She is a huge Instagram fan and was quite excited to see the new video clip feature that was recently introduced to the application. Her phone was running stock ICS and, unfortunately, Instagram video is not functional for anything less than Android Jellybean (at least that is my understanding). The video button doesn't appear in the application under ICS. I don't like messing with my wife's phone but I was forced to make the move to Jellybean.
First stop was PAC-man 4.1.2. The video option shows up in Instagram and videos can be recorded. However, when trying to apply filters the video won't play back properly (either dosn't play back, choppy, or pixelated) and 90+% of the time it ends up causing the phone to freeze/reboot. Not good.
Next stop was the new CM10.1 AOSP 4.2.2 rom. I noticed that video recording had been fixed with this rom. The video option shows up in Instagram and videos can be recorded, same as in PAC-man. The good news is that filters can somewhat be applied and the video will play back better with this rom. There are still issues with the play back causing some of the frames to dance around the screen, however, it no longers crahes the phone. It has crashed the Instagram application but, in general, things can somewhat work but not to the degree to which they should (and definitely not to the degree my wife would find acceptable). I have recorded and played back video using the stock camera app and everything functions smoothly with no hiccups so it is seems that the problem lies in how Instagram is interfacing with the playback capabilities of the phone, using a series of calls that the playback mechanism doesn't quite like. What, if anything, can I do to provide feedback to the developers of CM10.1 that would give them some indication of how Instagram is trying to work with the play back capabilities of the phone? Would a logcat give some indication? What kind of debugging would I need to turn on (if any)?
As a frame of reference, I use CM10.1 4.2.2 Maguro on my Samsung Galaxy Nexus phone. I have the Instagram app installed and the video recording capabilities work smoothly and without an issues within it. Applying filters to videos works perfectly and I haven't had a single crash. I know that this is different hardware but if there is anything that can be leveraged from that rom please let me know.
I must say that development of CM10.1 is moving along at a very rapid pace and, for the most part, it is functioning extremenly well and stable on my wife's phone. The only thing I noticed was that CM10.1 lagged only slightly when compared with PAC-man when responding to screen swipes. I'm sure this will improve with time and I am quite thankful to those developing it for breathing added life into this phone.
Again, I would like to get Instagram working smoothly with the HTC Vivid so suggestions as to what I need to provide to the developers would be greatly appreciated. I haven't made enough posts to the xda-developers forums so I am unable to post to the development threads. Any feedback I create will need to go thru here so hopefully I can get some assistance to get it to the right developers.
Edit: the new 0715 cm 10.1 has fixed the instagram video issues when applying filters to a video. Everything seems to be running smoothly now. My wife is asleep and doesn't know this yet, but I'm sure she'll be quite happy in the morning. Many thanks to the developers. Great job!
Sent from my Galaxy Nexus using Tapatalk 2
Screen flicker with New GMapps 7.0
Am getting a screen flicker 80% of the time during maps session (not lighting, actual flicker of maps). It is to the point of not being able to use maps at all. Anyone else?
Assuming not alone:
Appear to have solved it with "Disable HW Overlays", so can only assume this is related to the soft reboots, and associated memory map issue, as I would be surprised that GMaps wouldn't play well with 4.2.2.
!!!!!! NOT FULLY TESTED !!!!!!!
This patch is based on Tasssadar's hardboot patch for mako. And I borrowed some code (hardboot page address usage) from alvinhochun's Xperia M port. The kernel source is 9.2.A.0.295 from Sony. Thanks all of above!
Here is Tassadar's original thread which explains what is kexec hardboot and what it does. Apply this patch to your kernel source and it will be capable of booting another kernel/system without reflashing.
Note: KEXEC_HB_PAGE_ADDR doesn't need to be a certain value. In my tests, 0x88000000 and 0x88A00000 both work. However, I don't know if there are significant side effects... There is no ram_console entry in /proc/iomem... The default address calcuated by original patch is 0x88CE0000,which doesn't work, so I removed the calculation code and hardcoded the address (thanks alvinhochun)
Click to expand...
Click to collapse
Usage can be seen in the sh file attached. Sh file is modded on Tasssadar's. Kexec binary is also taken from his github. Thanks again!
Parameters:
--load-hardboot : load the kernel with hardboot request
--initrd : ramdisk path (For 2012 line, that's the ".cpio.gz" file)
--mem-min : where the kernel should be loaded to (lowest address). This is not certain,either. 0x82000000, 0x85000000 both work. You can try different values. (Is there any limitation to this? Plz tell me...) Normally 0x82000000 will be okay.
--command-line : command line for the guest kernel. Note that the arguments appended by bootloader (semcandroidboot.babe1324 etc)need to be added here manually.
Click to expand...
Click to collapse
Now I have successfully dual-booted stock 4.3(205) and OmniROM 4.4 (homemade):
1. re-partition external sdcard to 4 parts. 1 for regular data storage(mmcblk1p1), 1 for /system (mmcblk1p4), 1 for /data (p2) and 1 for /cache (p3).
2. mount /dev/block/mmcblk1p4 to USB storage in TWRP and "dd if=(9.2.A.1.205 system.ext4 extracted from FTF) of=(USB storage)" on computer. You can use a card reader also.
3. modify the fstab files in stock 205 ramdisk to change the devices for /system, /data and /cache. If you want to add recovery, edit their fstabs also. (PERMISSIONS FOR THESE FILES ARE REALLY IMPORTANT! All .rc and fstab should be 644, root:root. Otherwise it won't boot)
4. repack the ramdisk. Push the zImage and ramdisk to the phone and execute the sh file. The phone reboots and stock 4.3 loads.
5. rebooting the phone will go back to host ROM.
Click to expand...
Click to collapse
But there is one problem: in stock 4.3, Baseband is shown as "Unknown" and the phone gets no signal. On the host ROM, it works properly. It seems to be related to TA reading, but I can't think of anything wrong with this...Logcat shows three TA units were missing. But in host ROM, they are shown as missing too. Full logcat attached in zip. I didn't touch any file other than fstab, fstab.qcom and init.target.rc in 205 ramdisk. Stock 4.1 works like a charm though.
Anyone knows? Thanks in advance~
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
alanc.1996 said:
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
New build arrived (2014/05/21). See the separate thread. Following is the old message.
==================
At least it won't reboot ramdomly..but there may be some minor bugs.
Link: http://pan.baidu.com/s/1i3Hq4ip (Password: kpnn)
Internet connection is not very good here so uploading to devhost/mediafire is nearly impossible...
You need to flash the kernel first, then use the recovery to flash the ROM, then flash the kernel again. After system boots, push the modules file to /system/lib/modules
This is based on tital's port. Thanks a lot~
Later I will open a thread to introduce this ROM...
Cool! Will try it out!
Sent from my LT29i using XDA Premium 4 mobile app
Months ago, when I restored an Nandroid backup of 9.2.A.0.295, the same problem appeared. But at that time only mobile service was dead, while WiFi worked. Now mobile service and WiFi are all dead. The screen stops at "Turning on Wi-Fi". However, in dmesg & lsmod, I can see that WLAN driver module has been loaded, with MAC address changed correctly...And in Service Menu(*#*#SERVICE#*#*), Configuration in Service info is dead. Tapping on it will cause the app to stop responding. What is the point?
OK I tried 9.1.B.1.67 firmware. Everything works, including baseband, Wi-Fi and *#*#SERVICE#*#*... However, it's not so attractive as stock 4.3...
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
RpRAUC said:
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
Click to expand...
Click to collapse
As long as the kernel matches the ROM (phone operates normally when you install the custom kernel as usual), it should be okay...
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Galcactus said:
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This patch may work on T without any modification, except for the macro name in memory.h
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Galcactus said:
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
It's already perfectly working...
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Galcactus said:
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This is a little bit complicated... but I'll try to make a post about this in a few days.
The kernel commits should be the same for TX and T :
https://github.com/updateing/androi...mmit/3d4950e7d3a0cc1549e82fda6c1d961f83e04f4a
https://github.com/updateing/androi...mmit/8843e01fb1b6752768056589a510a2f8985c0884
Make this pretty later
You just made my day
Sent from my Nexus 6
I just confused myself. Should i be flashing the bootloader, radio, etc from a nexus factory image and then flash omni? I have been using 20150605 build without doing this. Should i do this for the nightlies?
subterfugium said:
Code:
I:operation_start: 'Flashing'
Installing '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'...
Checking for MD5 file...
MD5 matched
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:failed to verify against RSA key 0
E:failed to verify whole-file signature
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'
I guess zip verification fails because of test-keys or what does that zip verification stand for?
Click to expand...
Click to collapse
Honestly, I've never used zip verification for all the years I've been flashing ROMs and have never had any issues.
I'm probably wrong but.. My theory is that packed somewhere inside the zip you are trying to flash lies a key, which is compared next a second key once extracted. If they don't match it throws an error and aborts the operation.
Sent from my Nexus 6 using XDA Free mobile app
I've never used zip verification for this exact reason, and therefore have never looked into it. This sounds like something for the TWRP thread that @Dees_Troy could answer maybe.
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
The Rom OP is a bit bare of info. Thanks
530farm said:
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
Click to expand...
Click to collapse
Off the top of my head... battery icon customization, volume match orientation, volume wake, screenshot delete, advanced reboot menu, hide usb debugging icon, ambient display customization. Also, Omni is the only AOSP ROM where I don't get force closes when taking multiple HDR+ pictures in a row without pause.
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
I saw that the past few builds uploaded were all 0mb. Just wondering what's going on until the builds resume?
Gandalf said:
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
Click to expand...
Click to collapse
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Ngo93 said:
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
Click to expand...
Click to collapse
jira.omnirom.org :good:
glockliberty said:
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Click to expand...
Click to collapse
Updates to opendelta have not been merged yet
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
RanceJustice said:
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
Click to expand...
Click to collapse
The server is probably being slow. They just upgraded storage/cleaned it up a few days ago and it has been significantly faster, it might be your connection to the server or something else.
As far as a list of features, there isn't one to my knowledge but you can certainly check on gerrit to see what's been merged recently. Just flash it and see for yourself: highfive:
Does this rom have layers?
Omnirom 5.1.1 nightly sudden reboot+supersu freeze+bluetooth headset bugs
I installed Omnirom 3days ago and have to say; nice stuff. runs fluid, batterie's fine and overall i like user experience. BUT
I'm experiencing some bugs.
first of all sometimes there just are random sudden reboots. On stock rom this happened from time to time when battery was below 30% or something so i thought there has to be a powersaving feature or something in kernel that don't works correct.
Then i flashed TWRP+Omnirom and those sudden reboots started happening randomly; regardless of battery.
I googled and found that could be some setting that adapt display brightness(???) and/or some apps bugging/conflicting. and, from previous experience, i know that this could also be a hardware/battery failure(please not; can't send my phone back right now as i need it daily for work and my N5 has a broken touch )
i tried disabling that display feature and also installed and tested if 'Lux' has any impact on that as it, basically, does the same but no change.
i factory reseted my device multiple times and tried to find out what APP could force this but... right now there's only the bare minimum(contacts+ / messages+ / aquamail / maildroid / todoist /calengoo /business calender pro and google stock apps)and still same problem. sometimes even while calling what's very embarassing when having an important customer on phone ...
I gonna try Zen Kernel next just to see if different kernel with different cpu scheduler COULD make any difference.
Then the second bug is my bluetooth headset(Plantronics M165). Can't get it to pair. Before Omnirom this worked very well as it should. Now, most of time he finds nothing and sometimes he finds a mac address of the headset but not the name. Other bluetooth devices are working fine and the headset's still working perfectly well on my gf's HTC M8. Anyone any ideas?
Last bug i experienced is SuperSU. Always an app needs root i can't get SuperSU intercept my choice. I click on allow or deny but nothing happens and after 10seconds superSu autodenies(or allows; depends on settings )right after factory reset supersu just works fine but suddenly stops working. root's still there as i can perfectly tell supersu what to do in its settings. Only the on demand root question can't be answered. uninstalling/reinstalling supersu didn't change anything. It doesn't matter if i install supersu by playstore or by zip through recovery. also unrooting and rerooting doesn't help. only a factory reset helps; for a while.
I don't want to change my Superuser managment as i paid for the pro version ...
Hope to find some help here as it's one of my fav places for everything smartphone related since back in my tytn days
so much knowledge in here.
keep up the good work
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
nightfly.0684 said:
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
M builds will be ready soon enough :good:
great news
Do we get the Update for M through opendelta or is a factory reset + reflash needed?
and if i understand right you assume that the Bluetooth Problem should be gone with M?
would be nice as, right now, I sometimes have to pick up important calls while driving ... and... i don't like that at all....
would try the homemade M build IF i wouldn't need it daily for work. about time to repair my n5 i guess
Sent from my Nexus 6 using XDA Free mobile app